System and method of automatically displaying patient information

ABSTRACT

Methods, systems, and products improve healthcare of patients. An electronic patient chart is retrieved and displayed at a patient room computer system. The electronic patient chart is also displayed at a remotely-located primary computer system, such as a nurse&#39;s station or other monitoring party. The patient room computer system is linked to the remotely-located primary computer system such that updates to the electronic patient chart received at the patient room computer system are also updated at the primary computer system to permit monitoring.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/103,215, filed Apr. 15, 2008, and now issued as U.S. Pat. No.7,949,547, which is a continuation of U.S. application Ser. No.10/611,250, filed Jun. 30, 2003 and now issued as U.S. Pat. No.7,357,308.

FIELD OF THE INVENTION

The present invention relates to the medical industry and; inparticular, to methods of managing patient records. More particularly,the present invention relates to the manner in which patient records arestored and used, including the contemporaneously viewing and updating ofpatient charts during actual patient care activities.

BACKGROUND OF THE INVENTION

During a typical office visit to a physician or other medicalprofessional (hereinafter “healthcare professional”), whether in anoffice or a hospital, a separate patient chart is created for each newpatient. This chart lists all the relevant information related to thatpatient such as medical history and specific medical needs. The charttypically includes other pertinent information such as the patient'spersonal identification information such as their name, address, billinginformation, emergency contact, etc.

Indeed, the chart is the primary document maintained in most medicalarenas. During subsequent visits this chart is pulled and handed to thehealthcare professional for contemporaneously taking notes and making arecord of discussions and advice given to the patient. The chart alsotypically contains information related to prescriptions written by thehealthcare professional during particular visits. Since the chart is inpaper form, it is handed back and forth between assistants andsecretaries as part of the patient care process. Furthermore, such achart may be handed to or passed through the accounting department forproper insurance and patient billing.

Significant drawbacks related to these paper charts are encountered on adaily basis in numerous healthcare facilities. For example, paper chartsare often damaged, lost or misplaced. In particular, in a hospitalenvironment, the patient charts are easily confused and thereforemisplaced. In such an environment, the primary doctor often does notknow the patient personally as it may be the first time that particulardoctor has seen the patient such that the doctor may be unaware that thepatient chart is incorrect in some instances. Adding to this, sometimesthe patient is unable to communicate with the doctor such that thedoctor must rely on the chart handed her or located in the room with thepatient. Obviously, a lost or misplaced chart creates a very difficultsituation because the re-creation of such information is nearlyimpossible. Other times the situation may be time critical such thatre-creation of the information would simply take too long. Thus, a lostchart is not only time consuming but potentially dangerous as well.

Another significant problem associated with the paper charts relates tothe legibility of the handwritten notes. Indeed, failure to accuratelyread a medical chart may result in the improper prescription of certaindrugs, which can be very dangerous.

Furthermore, although not often recognized as a problem, the papercharts may in fact aid in the transmission of diseases as the charts arereused and passed from room to room without disinfection. Theinadvertent transmission of diseases is, of course, a dangeroussituation.

These problems all directly impact the safety and satisfaction ofpatients and the care that they are given and it is with respect tothese and other considerations that the present invention has been made.

SUMMARY OF THE INVENTION

The present invention relates to a computerized patient chart systemthat involves a patient room computer system for the contemporaneousdisplay and maintenance of patient medical information, i.e., edits andadditions to the patient chart. Since the patient room computer isavailable during the visit, the healthcare professional can enterinformation on the computer system to reduce errors associated withlegibility. Also, since the chart is kept on the computer system, papercharts are not used and therefore do not get lost as the system can bebacked up and saved in many different, and protected ways. Also, sincepaper charts are not being handled, the chance of disease transmissionis reduced. Further, since the system is computerized, different programmodules may be incorporated to double check the suitability ofinformation entered, e.g., the accuracy/appropriateness of prescriptionsfor a given patient, etc.

In accordance with other aspects of the present invention, the patientroom computer system is connected, via a network, to a primary computersystem. The primary computer system, in an embodiment, relates toanother computer system located at the nurse's station or some otherlocation. During a particular patient visit, the primary computer systemmay simultaneously display the patient chart (along with contemporaneousupdates) to improve the service provided to the patient. Further, othercomputer systems, such as a doctor's remote computer system, may accessthe information.

In accordance with certain aspects, the present invention relates tosystems and methods of automatically or semi-automatically loadingpatient chart information onto a patient room computer system. Thesystems and methods involve using the patient room computer system toobtain patient identifying information, then requesting the patientchart from a primary computer system. Upon receiving the patient chartfrom the primary computer system, the invention relates to displayingthe patient chart on the patient room computer system.

Obtaining the patient information may occur in several ways. Forinstance, since a patient is typically associated with a specific roomwithin the healthcare facility, the act of obtaining patient informationmay involve determining the room identification for the patient andusing the room identification, requesting the patient chart associatedwith the room. In an embodiment, the room identification information istransmitted to the patient room computer system automatically uponentering the room, e.g., by using cellular telephone technology. Inanother embodiment, the patient room computer system has bar-codereading capabilities and thus reads a bar-code, either as part of theroom providing room information as part of the patient providing patientidentification information independent of room information.

The invention may be implemented as a computer process, a computingsystem or as an article of manufacture, such as a computer programproduct. The computer program product may be a computer storage mediumreadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by acomputing system and encoding a computer program of instructions forexecuting a computer process.

A more complete appreciation of the present invention and itsimprovements can be obtained by reference to the accompanying drawings,which are briefly summarized below, to the following detaileddescription of presently preferred embodiments of the invention and tothe appended claims.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram illustrating the environment for the presentinvention including a networked system for entering and managing patientinformation.

FIG. 2 illustrates a computer system that may be utilized in anembodiment of the present invention.

FIG. 3 illustrates a more detailed view of a particular computer asshown in FIG. 2 including automatic entry and remote entry capabilitiesand a particular embodiment.

FIG. 4 illustrates a screen shot showing an exemplary graphical userinterface for displaying and editing an electronic patient chart inaccordance with an embodiment of the present invention.

FIG. 5 illustrates a screen shot showing another exemplary graphicaluser interface for displaying and editing an electronic patient chartusing a plurality of window controls in accordance with anotherembodiment of the present invention.

FIG. 6 illustrates software elements in an embodiment of the presentinvention.

FIG. 7 illustrates an exemplary healthcare professional's officeimplementing concepts of the present invention, including differenttypes of patient room computer systems.

FIG. 8 illustrates a flowchart of functional operations related toentering information into a patient chart and storing the same on aprimary computer system.

FIG. 9 illustrates a flowchart of functional operations related toloading an electronic version of a patient chart onto a patient roomcomputer system in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

The present invention relates to a computerized network in a healthcareenvironment. A distributed environment 100 incorporating aspects of thepresent invention is shown in FIG. 1. The environment 100 relates to adistributed network having at least one patient room computer system 102that communicates with at least one primary computer system 104. Theclient computer system 102 and the server computer system 104communicate using a communication protocol over the distributed network106. In one embodiment, the communication network 106 is an intranet. Inother embodiments, the network 106 utilizes the Internet. The patientroom computer system 102 is used to display an electronic orcomputerized version of a patient chart having patient information, andto edit the same, thereby eliminating the need for paper-based patientcharts.

The patient room computer system 102 receives and displays data enteredby the doctor or other healthcare professional providing patient care tothe patient. The system 102 allows the healthcare professional to enterthe information contemporaneously with the patient visit, i.e., duringor shortly after the patient visits the healthcare professional.

Although the healthcare professional typically enters such information,as may be understood, many different individuals may utilize this systemto record information related to a particular patient and/or visit,including nurses, administrators, staff employees, etc.

The patient room computer system 102 displays the patient chart for avisiting patient. In an embodiment, the healthcare professional canaccess the information by connecting to the network 106 and requestingthe chart for a particular patient. Access to the chart may require alogin name and password to be entered in order to access the patientinformation. An exemplary login screen for a particular patient, e.g.,John Doe, is shown as screen shot 108 in FIG. 1. This login providessecurity for the patient information as only those persons knowing thelogin name and password can access the information. Also, as shown inFIG. 1, the patient chart may be accessed from both the patient roomcomputer system 102 and the primary computer system 104. When accessingthe patient chart from the system 104, a similar login screen 110 isprovided for security purposes.

In another embodiment, such as when the patient room computer 102 is amobile device, the relevant patient information may be automaticallydisplayed upon entering the patient's room. Alternatively, the loginscreen may be automatically displayed. However, when the device is amobile device, some security may be relaxed since it is assumed theholder of the device is authorized to view patient information. Ofcourse, many other known security methods and procedures may beimplemented to protect the patient's privacy.

The automatic display of patient chart information upon entering thepatient's room may be achieved in different ways. For instance, in oneembodiment the patient room computer system 102 receives a wirelesscommunication from a transmitting/receiving devices (not shown) locatedin the patient's room upon entering that room. Consequently, the patientroom computer system recognizes that it has entered a new room uponreceiving a new signal. Using this room-identification information, thepatient room computer system 102 communicates, using similar wirelesscommunication technology with the primary computer system 104. Thesecommunications may enable the primary computer system to understand thelocation of the patient room computer system and hence, whichinformation should be downloaded and displayed on the patient roomcomputer system 102.

Alternatively, the patient room computer system may have bar-codereading capabilities. In such a case, the room may have an associatedbar-code, such as on door or in some other area of the room. Thus, thehealthcare professional need only scan the bar code to identify the roomlocation, transmit the same to the primary computer system 104 to thusreceive the relevant patient information in such a semi-automaticmanner.

In yet another embodiment, the patient may have an associated bar-code,e.g., printed on a bracelet, and the healthcare professional need onlyscan this information. In this embodiment, the room location is notrelevant, as the primary computer system can download the properinformation for the patient independent of where the patient roomcomputer system is located.

In a particular embodiment of the present invention, when both computersystems 102 and 104 have correctly accessed a patient's chart, thedisplays are linked and information provided on one system 102 or 104,is substantially simultaneously shown on the other system 104 or 102respectively. Providing the simultaneous display on the two systems 102and 104 provides a monitoring capability for the healthcare facility. Inyet another embodiment, some of the monitoring functionality can behandled by the computer system, e.g. 102 or 104, itself. More details onsimultaneous display and the automated monitoring functions can be foundin U.S. patent application Ser. No. 10/610,777 (since abandoned),incorporated herein by reference for all that it discloses and teaches,filed concurrently herewith, and assigned to the Assignee of the presentapplication.

The computer systems, such as 102 and 104 may be represented by thecomputer system 200 shown in FIG. 2. The system 200 has at least oneprocessor 202 and a memory 204. In its most basic configuration,computing system 200 is illustrated in FIG. 2 by dashed line 206encompassing the processor 202 and the memory 204. Additionally, system200 may also include additional storage (removable and/or non-removable)including, but not limited to, magnetic or optical disks or tape. Suchadditional storage is illustrated in FIG. 2 by removable storage 208 andnon-removable storage 210. Computer storage media, such as memory 204,removable storage 208 or non-removable storage 210 includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer readableinstructions, data structures, program modules or other data. Memory204, removable storage 208 and non-removable storage 210 are allexamples of computer storage media. Computer storage media includes, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by system 200.Any such computer storage media may be part of system 200. Depending onthe configuration and type of computing device, memory 204 may bevolatile, non-volatile or some combination of the two.

System 200 may also contain communications connection(s) 212 that allowthe device to communicate with other devices. Additionally, system 200may have input device(s) 214 such as keyboard, mouse, pen, voice inputdevice, touch input device, etc. Output device(s) 216 such as a display,speakers, printer, etc. may also be included. All these devices are wellknown in the art and need not be discussed at length here.

Computer system 200 typically includes at least some form of computerreadable media. Computer readable media can be any available media thatcan be accessed by system 200. By way of example, and not limitation,computer readable media may comprise computer storage media andcommunication media. Communication media typically embodies computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. Combinations of any of the above should also be includedwithin the scope of computer readable media.

As stated, the input devices 214 may include many different types ofinput devices. Some exemplary devices 214 are represented in FIG. 3.FIG. 3 also illustrates alternative input device connections 218.Although not shown in FIG. 2, the input connections 218 relate to theconnection elements associated with the computer 200 and moreparticularly 206 to allow external input devices to communicate with thecomputer 206. For instance, the system 206 may receive input from moretraditional devices 220 such as keyboard, mouse, pen, handwritingrecognition, alphanumeric, voice input device, touch input device, etc.In order to receive input information from such devices, inputconnections 222 are used. The input connections 222 relate to thecomputer connections, whether serial, parallel, USB, AT, PS/2, etc. forreceiving information from one of the devices 220.

In the embodiment shown in FIG. 3, other input devices are also used toprovide input information to computer 206. For instance, a bloodpressure sensor/monitor 224 may be connected to a blood pressure monitorinput connection 226 for relatively automatically providing bloodpressure information to the computer system 206. Similarly, a heart ratesensor/monitor 228 may be connected to a heart rate monitor inputconnection 230 for relatively automatically providing heart rateinformation to the computer system 206. Additionally, anelectrocardiogram (EKG) sensor/monitor 232 may be connected to anelectrocardiogram (EKG) monitor input connection 234 and a temperaturesensor monitor 236 may be connected to a temperature monitor inputconnection 238 for relatively automatically providing EKG informationand temperature information to the computer system 206, respectively.Furthermore, as may be understood, other items may also be used asindicated by ellipses 240 and 242.

In operation, during a visit, the healthcare professional retrieves apatient's chart on the patient room computer system, such as patientroom computer system 102 shown in FIG. 1. A screen shot of an exemplarypatient chart 300 is shown in FIG. 4. In this embodiment, the chart 300is divided into at least three areas: a history area 302, a present-daychecklist area 304, and a present diagnosis section 306. The chart alsohas a title bar 308 describing the patient and having a user-interfacecontrol 310 that allows the user to close the chart 300 when selected.The chart may further include user interface controls 312 and 314 thatallow the user to update the chart, e.g., save the changes into memoryusing the “complete” control 312 or cancel and not save the changesusing the “cancel” control 314.

In the history area 302, as shown in FIG. 4, many different historicalitems or information may be displayed. For instance a summary of recentvisits may be displayed (as shown in FIG. 4). Alternatively, drugallergies may be shown, number of visits per year, recent types ofprescribed medication, or almost any other type of historical data maybe displayed. The area 302 may also include user-interface controls (notshown) to scroll through historical items or to select certain types ofitems to display. In an embodiment, the historical area may not beedited such that no accidental changes can be made.

The present-day checklist area 304, titled “Nurse's Checklist” includestwo portions, a checklist portion 316 and a notes section 318. Thechecklist portion 316 provides text boxes for entering informationrelated to the patient on the day of the visit. That is, when visiting adoctor or another health professional, a nurse typically gathersinformation about the patient, such as height, weight, blood pressure(BP), temperature and/or potentially other information. The area 304provides a convenient means for entering the information and a checklistfor reminding the nurse of the various items to be tested and/orinformation to be gathered. It is foreseeable that this area would becustomizable to a particular practice depending on preferences of aparticular healthcare professional. For instance, a podiatrist wouldcare about different information than a general practice physician andthus the items in area 316 may be different for different healthcareprofessionals.

In addition to checklist portion 316, the nurse can enter notes to thehealthcare professional by editing the notes section 318. That is,during a typical visit, the nurse visits with the patient first,gathering information in area 316 and to find out the purpose of thevisit. The nurse can quickly make a note of the purpose of the visit,e.g., “pain in stomach” or “high temperature”, etc. Subsequently, thehealthcare professional is able to quickly ascertain the issues byreading the notes section 318. Of course, any other relevant notes maybe entered into section 318.

The third area of the chart 300 relates to the healthcare professional'sarea 306. In the example shown in FIG. 4, the area 306 is titled“Doctor's Notes” and is divided into two sections, diagnosis area 320and notes area 322. The diagnosis area 320 is generally reserved for thehealthcare professional's specific diagnosis and advice given to thepatient, as well as any prescriptions written for the patient. Thisinformation may become part of the permanent chart for the patient. Thehealthcare professional also has a notes section 322 for taking notesregarding the visit. This information may or may not become part of thepermanent chart for the patient.

In another embodiment, different portions of a patient chart, such aschart 400, are presented as separate window elements, as shown in FIG.5. Chart 400 incorporates a title bar 402 and a user-interface controlelement 404 to close the chart when selected. The chart 400 also has aplurality of sub-window elements, such as elements 406, 408 and 410. Inthis example the sub-window elements 406, 408 and 410 correspond to thedifferent chart areas 302, 304 and 306 associated with chart 300 shownin FIG. 4. That is, element 406 is a relevant history window elementthat comprises similar information as relevant history area 302. Also,the window element 408 comprises similar information as the portion 304,including a checklist area and a notes area. Further, window element 410is similar to the portion 306 shown and described in conjunction withFIG. 4.

As discussed above, FIGS. 4 and 5 illustrate examples of potentialscreens or graphical user interface elements that may be implemented inan embodiment of the present invention as part of the overall userinterface. The purpose of these user interface elements is to displayrelevant information in a meaningful manner as well as provide ameaningful way to enter new, updated patient information so that it canbe stored as part of the patient's medical chart and thus medicalhistory. As may be appreciated, many other user interface elements,including but not limited to, pop up screens, menus, pop up menus,control elements, etc. may be designed to achieve this function.Consequently, FIGS. 4 and 5 are intended to be mere examples ofelectronic versions of patient chart information and the user interfacesfor reading and editing the same.

The logical operations of the various embodiments of the presentinvention may be implemented (1) as a sequence of computer implementedsteps running on one or more computing systems and/or (2) asinterconnected machine logic modules within the computing systems.Accordingly, the logical operations making up embodiments of the presentinvention described herein are referred to variously as operations,acts, steps or modules as shown and described more fully below.

FIG. 6 illustrates a software/hardware environment 600 incorporatingaspects of the present invention. The environment 600 includes separatemodules that perform functional operations in accordance with thoseaspects and wherein the modules are communicably connected as needed toperform certain functions as shown in FIG. 6. In general, theenvironment 600 comprises a patient room computer system or layer ofsoftware 602 and a primary computer system or layer of software 604,which, in one embodiment correspond respectively to the patient roomcomputer system 102 and the primary computer system 104 shown in FIG. 1.The patient room computer system software 602 communicates with theprimary computer system software 604 to automatically receive and laterstore patient charts. The primary computer software 604 accesses patientrecord databases, such as database 606, and, in other embodiments, othercomputer systems (not shown) to provide information to the patient roomcomputer system software and to manage other patient needs. In theembodiment shown in FIG. 6, the management module 607 relates to theapplications or other program elements used and accessed by a user tostore, retrieve and otherwise manage the patient records stored indatabase 606.

The patient room computer system software layer 602 has a user interfacemodule 608 to both provide information to a user, e.g., through amonitor, speakers or some other device and to receive data from a user,e.g., through a keyboard, touch screen, etc. The different types ofinput devices are described above in conjunction with FIGS. 2 and 3. Theuser interface module 608 provides the software functionality to receivedata and display the same to the user. As may be appreciated, the userinterface module 608 further includes both an input module 609 and adisplay module 611. The input module 609 may be used by a user of thepatient room computer system to manually request a particular patientchart, to provide room or patient identification information in therequest for the chart, to provide security related identificationinformation and/or to simply enter updates to a particular patient'schart. The display module 611 is used primarily to display requestedinformation such as a patient's chart.

The patient room computer system software layer 602 also has anautomatic interface module or modules 610. These modules providesoftware support for the automatic data entry provided from some othersystem, such as the systems shown and described in conjunction with FIG.3. For instance, in an embodiment, the blood pressure monitor may beconnected to a computer system for reading, storing and displaying bloodpressure. This monitor may be connected to the patient room computersystem as discussed above in conjunction with FIG. 3 to transfer bloodpressure information to the patient room computer system. Whenconnected, the patient room computer software modules 610 provide thesoftware communication support to allow the transfer of this informationto the patient room computer system. Other modules 610 may beimplemented to receive information from other sensors or monitors asshown in FIG. 3.

In one embodiment, the user interface module 608 receives data from theuser and stores the information locally. In another embodiment, theinformation is transmitted to the software system 604 for storage on theprimary computer software system. In order to transmit the informationto the primary computer system software layer 604, the patient roomcomputer system software layer 602 has a communication module 612. Thecommunication module 612 communicates with communication module 614located on the primary computer system software layer. In an embodiment,the communication modules 612 and 614 communicate over an intranet. Inyet another embodiment, the modules 612 and 614 communicate over theInternet, or some other network configuration. In other embodiments thecommunication connection between 612 and 614 is wireless, while otherembodiments employ non-wireless technology.

In addition to the communication module 614, the primary computer systemsoftware layer may incorporate many other software elements. Forexample, the layer 604 has a user interface module 616. The userinterface module 616 is similar to the user interface module 608 in thatit provides software support for receiving data from a user anddisplaying or providing information to the user. The actual module 616may differ from module 608 in that the systems may have different userinterface elements, e.g., a touch screen instead of a keyboard, or amouse instead of a pen device, etc.

Another functional module that might exist on the primary computersystem software layer 604 relates to an inventory database 618. Theinventory database may house information related to various items keptin local inventory, e.g., medicine, samples, medical supplies, etc. Auser may access such information though the user interface module 616.

With respect to the patient record database 606, it includes the variouspatient charts as well as other patient-related information. Inoperation, the healthcare professional accesses the patient chart,stored in the database 606, and upon making changes, stores the chartback to the record database 606.

In order to access the proper patient chart, the patient room computersystem software 602 and its communication module 612 requests a patientchart from the primary computer system software 604. In order to accessthe proper patient chart, the patient room computer system softwarelayer 602 must provide some identifying information to the primarycomputer system software layer 604. In some embodiments, the user of thepatient room computer system may simply type or enter the requestedinformation, such as the patient's name, in order to allow the primarycomputer system to access and send the proper information. Upon enteringthis information, the user may then manually request the patient chartby choosing a request control on the user interface which, in turncauses a communication module 612 to request the proper patient chartfrom the software layer 604.

In other embodiments, the patient room computer system software layer602 utilizes a location/patient identification module to determine theidentifying information needed to request the proper patient chart. Inone embodiment, the identification module 620 communicates with apatient room transmitter/receiver module 622. In this embodiment, thepatient room computer system substantially constantly transmits andreceives information in a manner similar to a cellular telephone. Theconstant transmission and receipt of information allows the patient roomcomputer system to receive information from the transmitter 622 whichmay be located in a patient room.

This transmitter 622 provides information to the patient room computersystem software 602, and in particular module 620, such as the roomnumber information. The room number information may then be used in asubsequent request for patient chart information. In this embodiment, itis contemplated that the primary computer system can match the roomnumber with the patient staying or waiting in that room such that theproper patient information can be provided to the patient room computersystem software layer 602.

Also, it is contemplated that since the identification module maysubstantially constantly receive information from a patient roomtransmitter 622, the patient room computer system software layer mayrequest a new patient chart when the room information changes, e.g.,when the patient room computer system is moved from room to room. Thus,the display provided by the user interface module 608 may automaticallybe updated when the patient room computer system enters a new room witha different patient's information.

In other embodiments, the room identifying information may be entered bythe user, either manually or automatically. Manually entering the roominformation involves the user manually typing or selecting the roominformation from a list. Automatically entering the room informationinvolves other means of entering room information, such as by providinga bar-code reader as part of the patient room computer systemidentification module. In such a case the user may scan a room bar code624 located on the door of the room or in some other convenientlocation. Bar codes and bar code readers are well known to those skilledin the art. Upon scanning the bar code, the patient room computer systemcan request the proper patient chart using the entered room information.

In yet another embodiment, the patient may have an associated bar code626. The bar code may be printed on a bracelet or some other itemconnected to the patient's body or worn by the patient. In such a casethe identification module is equipped with a bar code reader and therequest for information includes the actual patient identificationinformation. Thus, the room number is not necessary for obtaining theproper patient chart and providing the same to the patient room computersystem software layer 602.

An exemplary healthcare professional's office 700 utilizing aspects ofthe present invention is shown in FIG. 7. Although described as anoffice, is should be recognized that this may relate to a portion of ahospital, clinic or some other patient care facility. In particular, theoffice 700 includes three patient rooms 702, 704 and 706. The patientrooms are separate meeting rooms where the healthcare professional willmeet with different patients. The office 700 also has a nurse's station708. The station 708 may have many different elements, including filingcabinets, medicine cabinets, etc. The nurse's station 708, in anembodiment, has one or more nurses or other support staff present duringpatient visits.

In the exemplary environment shown in FIG. 7, located inside each of thepatient rooms 702, 704 and 706 is a computer system. As shown in FIG. 7,the computer may be in the form of a workstation 710 (patient room 702),a pen computer 712 (patient room 712), or a hand-held computer system714 (patient room 706). Each of the different computer systems 710, 712and 714 communicate with a primary computer system 716. In theembodiment shown in FIG. 7, the primary computer system is located inthe nurse's station 708. The different computers 710, 712 and 714 areshown in FIG. 7 to illustrate that many different types of computersystems may be used in accordance with the present invention. Indeed,many other types of computer systems that are not shown may also be usedas patient room computer systems, as long as it communicates with theprimary computer system to send and receive patient record or chartinformation.

As may be understood, the computer system 710 represents an example of apatient room computer system 102 shown in FIG. 1. As shown, the computer710 is a workstation designed to remain within the patient room 702,i.e., it is not mobile. The workstation 710 may be used to enterinformation during a patient visit and to display a patient's chart to auser, among other things, as discussed above. In this embodiment, theworkstation 710 is connected via wires to the primary computer system716, i.e., it is hard-wired to the primary computer system 716. Inanother embodiment, the workstation 710 may be connected to anintermediate server computer system (not shown). In such an embodiment,the primary computer system 716 would also be connected to the servercomputer system (not shown) such that the workstation 710 and theprimary computer system 716 communicate with each other.

Office 700 also demonstrates two other types of patient room computersystems 102, i.e., pen computer system 712 and hand-held computer system714. The pen computer system 712 relates to a computer system that hasdifferent input functionality, such as a pen input instead of, or inaddition to, a more traditional keyboard/mouse input system. Thehand-held computer system 714 relates to a portable computer system thata healthcare professional may carry from room to room. The hand-heldcomputer system may have a touch screen and/or other types ofinput/output functionality that is different from other patient roomcomputer systems 710 and 712.

One difference between the systems 712 and 714 from the workstation 710,as shown in FIG. 7, is that the systems 712 and 714 are meant toillustrate the use of wireless computer systems that communicate withthe primary computer system. As such, the pen computer system 712 andhand-held computer system 714 transmit information in a wireless mannerto a receiver (not shown) which then communicates the information to theprimary computer system 716. The receiver may be located in or on theprimary computer system 716 or as part of another system, such as aserver system (not shown). Repeaters may also be employed to aid in thesending and receiving of such information.

Importantly, in an embodiment, the primary computer system also haswireless capabilities to transmit information to the pen computer 712and/or the hand-held computer system 714. As a result, the systems 712and 714 receive important information related to a patient from theprimary computer system when necessary. Furthermore, when using a mobilesystem, the device may be used from room to room, automaticallyreceiving and displaying information related to the relevant patient,independent of which room the patient is located.

In an embodiment, the systems 710, 712 and 714 communicate with theprimary computer system 716 via a local intranet system. However, inother embodiments, the systems 710, 712 and 714 may communicate with theprimary computer system 716 via a wide area network, and in some casesthe network is the Internet. As such, a health professional may visit apatient in another building, such as a hospital, or at their home, andthe health professional may communicate with the primary computer system716 to both transmit information and receive information.

FIG. 8 illustrates a flowchart of functional operations related toentering information into a patient chart and displaying the same on aprimary computer system. Initially, flow 800 begins with load operation802. Load operation loads patient record information onto a patient roomcomputer system, such as patient room computer system 102 shown anddescribed in conjunction with FIG. 1 above. In an embodiment, before thepatient record or chart can be loaded on the patient room computersystem 102, the chart must be entered onto a primary computer system,such as system 104 shown and described above in conjunction with FIG. 1.Many known methods of entering data may be implemented when initiallyloading the information onto the primary computer system, e.g., typingthe information or scanning the information may be exemplary data entrymethods.

Once a patient's chart has been loaded on the primary computer system,load operation 802 loads the chart on the patient room computer system,such as system 102. In an embodiment, a healthcare professional uses thepatient room computer system 102 to access the chart. Such a process mayinvolve the transmission of a request to the primary computer system,including the type of information requested, e.g., a patient's chart,and the name of the patient. In response, the primary computer systemmay require some identification information, such as a login name andpassword for security purposes. Upon providing the identificationinformation, the primary computer system transmits the requestedinformation to the patient room computer system, completing loadoperation 802. At this time, the healthcare professional has access tothe requested patient's chart. Although flow 800 relates primarily withthe loading of a single patient record onto a patient room computersystem, in practice many different patient records may be loaded ontothe computer system during a session and later recalled individuallywhen needed. More details on automatic and semi-automatic loading and/ordownloading of patient information 802 information are discussed belowin conjunction FIG. 9.

Next, edit operation 804 edits the patient's chart. During a typicalscenario, the healthcare professional edits the chart during thepatient's visit. Although this step may occur following the visit, suchlate entry reduces the ability to improve the efficiency of the visit,as information will not be shared with other computer systems during thevisit. Therefore, it is contemplated that this information will mostlikely be entered during the visit.

In the embodiment shown in FIG. 8, upon entry of information into thepatient's chart, transmit operation 806 transmits the update informationto the primary computer system. Upon receiving the information, storeoperation 808 stores the updates on the primary computer system. Inother embodiments, upon receiving and storing transmitted information,another step of displaying the updated information on the primarycomputer system may be implemented. Displaying the information allowsfor a nurse or other individual to monitor the updates to the chart andprovide improved service to the patient by anticipating different needssuch a medicine needs, medical supply needs, and/or billing needs. Moredetails on the simultaneous display/monitoring of the updatedinformation can be found in U.S. patent application Ser. No. 10/610,777(since abandoned), previously incorporated by reference.

FIG. 9 illustrates a flowchart of functional operations related toloading and displaying of a patient chart on a patient room computersystem, such as system 102 shown in FIG. 1, in accordance with anembodiment of the present invention. Prior to flow 900, it is presumedthat an electronic version of a patient chart has been created andstored on a computer system, such as primary computer system 104 shownin FIG. 1. Alternatively, the electronic version of the patient chartmay be stored elsewhere, yet the primary computer system has access tothat patient chart. Also, the patient chart may be recalled using properidentifying information, such as the patient's name, social securitynumber, or in some cases, the room number associated with the room thepatient is located.

Initially flow 900 begins with enter operation 902 wherein thehealthcare professional desiring the patient chart enters the patientroom. The patient room in this scenario is the room in which the patientis receiving treatment or is otherwise located. In general, the enteroperation 902 may also relate to the patient room computer system beingcarried into the patient room as well. Indeed, it is contemplated thatthe healthcare professional carries a patient room computer system fromroom to room.

Next, obtain operation 904 obtains the patient identifying information.Obtain operation 904 relates to the entering of patient informationwherein the patient information relates to either patient-dependent dataor patient-independent data. The term, “patient-dependent data,” as usedherein relates to data that is unique to the patient and is relativelypermanent such that no other patient shares this information, e.g., thepatient's name, social security number, address, telephone number orsome combination of the above. The term, “patient-independent data”relates to other identifying features that may be unique to the patientfor a short period of time, such as the patient's room number while thepatient is in the hospital or doctor's office, a bar-code value, etc.Obtaining this identifying information allows the patient room computersystem, such as 102 shown in FIG. 1, to request the proper patient chartfrom the primary computer system, such as 104 (FIG. 1).

Obtain operation 904 may occur in many different ways. In oneembodiment, the user of the patient room computer system simply entersthe room or patient identifying information into the patient roomcomputer system. In another embodiment, a bar code is associated with aroom and/or a patient. Using a bar-code reader communicably attached tothe patient room computer system, the bar code may be read and thusobtain the patient identifying information. In yet another embodiment,the patient room computer system may receive a signal from a transmitterlocated in the patient room. The received signal, in this case, includesroom (and therefore patient) identifying information.

Upon obtaining the patient identifying information, send operation 906sends a request for the patient chart. Send operation 906 relates to thepatient room computer system communicating with the primary computersystem. Additionally, the request includes patient identifyinginformation to enable the primary computer system to retrieve the properpatient chart. Following send operation 906, receive operation 908receives the request. Receive operation 908 relates to the primarycomputer system receiving the request from the patient room computersystem. Many known protocols and communication platforms may be used toimplement this send/receive communication.

Upon receiving the patient chart request, locate operation 910 locatesthe patient chart based on the identifying information. Locate operationrelates to a computerized method of searching stored records in apatient chart database, such as database 606 shown in FIG. 6. Using theidentifying information, locate operation is able to uniquely identify,and retrieve the proper patient chart. Once located, send operation 912sends the chart to the patient room computer system, which in turnreceives the chart at receive operation 914.

Next, display operation 916 displays the patient chart. Displaying thepatient chart may involve the display of information as shown anddescribed above in conjunction with FIGS. 4 and 5. Additionally, flow900 may further include a level of security (not shown) that requiresthe user to enter a user name and password before either sending arequest for a patient chart 906 or displaying a received patient chart916, or both. Depending on the security level, the authorization processmay be located either on the patient room computer system or on theprimary computer system, or both.

Following display operation, the flow 900 ends at end operation 918.Although not shown in FIG. 9, it is contemplated that once the chart isdisplayed, the healthcare professional is able to manipulate orotherwise edit the chart. Upon editing, the updates are transmitted backto the primary computer system to be stored and therefore managed.

Using the above methods and system, patient medical information, and inparticular, patient charts can be safely stored and backed up since suchdocuments are kept electronically. Also, the charts can be displayed orotherwise provided to a healthcare professional relatively quickly,i.e., automatically or semi-automatically without requiring the manualsteps of searching for a paper chart, pulling the paper chart andhanding the paper chart to the healthcare professional. Also, sincepaper charts are not handed back and forth, the chances of inadvertentlytransmitting diseases are reduced. Moreover, given that the electronicpatient charts of the present invention are supplied based on requestsusing patient identifying information, whether patient-dependent orpatient-independent, the chances of retrieving the wrong patient chartare greatly reduced.

It will be clear that the present invention is well adapted to attainthe ends and advantages mentioned as well as those inherent therein.While a presently preferred embodiment has been described for purposesof this disclosure, various changes and modifications may be made whichare well within the scope of the invention. Numerous other changes maybe made which will readily suggest themselves to those skilled in theart and which are encompassed in the spirit of the invention disclosedand as defined in the appended claims.

The invention claimed is:
 1. A method, comprising: receiving, at amobile device, a wireless room identification information signaltransmitted from a transmitter, the wireless room identificationinformation signal specifying information that identifies a room numberassigned to the room and a wireless network; communicating, by themobile device, with a remotely-located computer system via the wirelessnetwork; automatically transmitting, from the mobile device, a requestvia the wireless network after a detection of the wireless network, therequest specifying the room number and requesting an electronic patientchart associated with the room number; receiving, by the mobile device,the electronic patient chart, the electronic patient chart received inresponse to the request specifying the room number; automaticallygenerating, by the mobile device, a first display of the electronicpatient chart in response to receipt of the electronic patient chart;generating, at the remotely-located computer system, a second display ofthe electronic patient chart; linking, by the mobile device, the firstdisplay of the electronic patient chart with the second display of theelectronic patient chart by the remotely-located computer system suchthat the electronic patient chart is displayed by both the mobile deviceand by the remotely-located computer system; receiving, at the mobiledevice, updated information entered into the electronic patient chartdisplayed by the mobile device; and updating the second display of theelectronic patient chart at the remotely-located computer system withthe updated information to permit remote monitoring of changes to theelectronic patient chart made at the mobile device.
 2. The methodaccording to claim 1, further comprising associating the electronicpatient chart to the room number.
 3. The method according to claim 1,further comprising associating the electronic patient chart to apatient.
 4. The method according to claim 1, further comprisingreceiving the request for the electronic patient chart.
 5. The methodaccording to claim 1, further comprising associating the transceiver tothe room number.
 6. A system, comprising: a hardware processor; and amemory device, the memory device storing code, the code when executedcausing the hardware processor to perform operations, the operationscomprising: receiving a wireless signal broadcast from a transmitterassociated with a room, the wireless signal comprising information thatidentifies a wireless network and a room number assigned to the room;recognizing the wireless signal as entry into the room; communicatingvia the wireless network with a remotely-located computer system;automatically transmitting, in response to detection of the wirelessnetwork, a request via the wireless network, the request specifying theroom number and requesting an electronic patient chart associated withthe room number; querying an electronic database for the room number,the electronic database electronically associating electronic patientcharts and room numbers including an electronic association between theelectronic patient chart and the room number; retrieving the electronicpatient chart having the electronic association with the room numberspecified in the request; routing the electronic patient chart from theremotely-located computer system to the transmitter for transmission viathe wireless network; receiving the electronic patient chart sent viathe wireless network in response to the request specifying the roomnumber; automatically generating a first display of the electronicpatient chart in response to receipt of the electronic patient chart;establishing a monitoring link to the remotely-located computer system;linking the first display of the electronic patient chart with a seconddisplay at the remotely-located computer system; receiving updatedinformation input into the electronic patient chart; sending the updatedinformation to the remotely-located computer system for monitoringupdates to the electronic patient chart; and updating the second displayof the electronic patient chart at the remotely-located computer systemwith the updated information to permit monitoring of changes to theelectronic patient chart.
 7. The system according to claim 6, whereinthe operations further comprise associating the electronic patient chartto the room number.
 8. The system according to claim 6, wherein theoperations further comprise associating the electronic patient chart toa patient.
 9. The system according to claim 6, wherein the operationsfurther comprise receiving the request for the electronic patient chart.10. A memory device storing instructions for that when executed cause ahardware processor to perform operations, the operations comprising:receiving, at a mobile device, a wireless signal broadcast from atransmitter assigned to a room, the wireless signal identifying awireless network and a room number assigned to the room; communicatingvia the wireless network between the mobile device and aremotely-located computer system; automatically transmitting, inresponse to receipt of the wireless signal, a request via the wirelessnetwork for an electronic patient chart associated with the room number;routing the request from the transceiver over another network to theremotely-located computer system; querying an electronic database forthe room number, the electronic database electronically associatingelectronic patient charts and room numbers including an electronicassociation between the electronic patient chart and the room numberidentified in the request; retrieving, by the remotely-located computersystem, the electronic patient chart having the electronic associationwith the room number; routing the electronic patient chart from theremotely-located computer system to the transmitter for transmission viathe wireless network to the mobile device; receiving the electronicpatient chart at the mobile device; automatically generating a firstdisplay of the electronic patient chart by the mobile device in responseto receipt of the electronic patient chart; generating a second displayof the electronic patient chart by the remotely-located computer system;establishing a monitoring link between the mobile device and theremotely-located computer system; linking the first display of theelectronic patient chart at the mobile device with the second display ofthe electronic patient chart by the remotely-located computer systemsuch that the electronic patient chart is displayed by both the mobiledevice and by the remotely-located computer system; receiving updatedinformation input into the electronic patient chart at the mobiledevice; sending the updated information from the mobile device to theremotely-located computer system for monitoring updates to theelectronic patient chart; and updating the second display of theelectronic patient chart at the remotely-located computer system withthe updated information to permit monitoring of changes to theelectronic patient chart made at the mobile device.
 11. Thenon-transitory memory according to claim 10, wherein the operationsfurther comprise associating the electronic patient chart to the roomnumber.
 12. The non-transitory memory according to claim 10, wherein theoperations further comprise associating the electronic patient chart toa patient.
 13. The non-transitory memory according to claim 10, whereinthe operations further comprise receiving the request for the electronicpatient chart.